Version control system for data

Logs commits of file changes retrievable at any time

Version control

Collaborate

Storage for every possible file type, e.g. Supp Material

Dynamic loading of stored links and programs

require(RCurl)
script <- getURL("https://raw.githubusercontent.com/darwinanddavis")
eval(parse(text = script))

Fork and clone a plethora of public data, code, material

Reproducible

Unlimited

Transparent

Shareable

Avoid spaces and CamelCase

• e.g. 'my data.csv', 'My Data.csv' POOR
  
• e.g. 'mydata.csv', 'my_data.csv' GOOD

Annotation

p <- rep(rnorm(100),20) # this is well annotated code  

Tab is your friend

cd change working dir. cd .. move one level up

pwd print current working dir

ls list files in working dir

mkdir newfolder make new working dir

touch text.txt create new file

cp source destination
copy files from source to destination. e.g. cp /Users/mydir/README.txt ~/Documents

cp -R source destination
copy all folders, subfolders, and files from source to destination

mv source destination
move files or folders from source to destination (no need for -R)

cp ~/Desktop/*.rtf ~/Documents
move multiple files with the * wildcard, which copies all .rtf files. The tilde (~) symbol is a shortcut for your Home folder, which contains '/Desktop'.

mv ~/Desktop/MyFile.rtf ~/Desktop/MyFile-old.rtf
cp ~/Desktop/MyFile.rtf ~/Documents/MyFile-old.rtf
rename files

1. Create a repo

2. Create and stage your files

- add and commit your files

3. Push to a remote github repo

- push your files

Open Terminal/cmd

cd ~/Documents/ # change working dir     
ls # list dir contents      

Open Finder/Windows. Make a new project on your local comp.

# create new project  
cd ~/Documents
# create new file 
touch test.txt  
open test.txt  
# make a new folder  
mkdir newgit  
# navigate to that folder  
cd newgit
ls -a  

Create a new file in the command line

# navigate to your new git repo  
pwd  
cd ~/Documents/newgit

# move the new file into the git repo      
mv ~/Documents/test.txt ~/Documents/newgit
ls  

Initialise your new local repo

# init git
git init  

Add the files in your folder to the local git repo

# add the files to the git  
git add . # the '.' adds everything 
git add test.txt # adds individual files  
git status # check what git is doing    

Stage the files for the commit

# add the files to the git  
git commit -m 'init commit' # -m adds a message  

We've now added and staged files to a local repo. Version control!

Let's check the changes

git log # recent git activity

Now we push the changes we made from our local repo to our Github cloud.

1. Create a new Github repo. Name is using best practise, e.g. no spaces
   
2. Don't create a README

• Uncheck the box 'Initialise this Github with a README'

First, copy the Github repo link you want to push to. Select either https or SSH (requires key access).

Then push your staged (commit) files from your local repo to the remote repo

# set the new remote repo
git remote set-url origin "your github repo"  
git remote add github "your github repo"  
# see what remote repo you have
git remote -v  
# push changes from local repo to remote repo 
git push -u github master

This creates a git repository on your local machine complete with version control.

Every version of every file for the history of the project is grabbed by default when you run git clone.

git clone "github url" "new repo name (optional)"
# e.g. git clone https://github.com/darwinanddavis/UsefulCode mynewrepo 

local git (version control on your comp)

git add . # adds all files to git. replace '.' with filename for individ files
git commit -m 'redo intro' # '-m' = message 

remote git (version control on your github)

# after the above steps ^ 
git remote set-url origin "link to existing github repo" # talk to github   
git remote -v  # verify the remote repo (optional)
git pull origin master  # pull the last commit to match your local changes 
git push -u origin master # push changes from local repo to remote repo 

git log # check recent activity. this is where you retrieve gits, e.g. '0dg45'
git status # check git status at any time  

If in doubt, ask the internet

Re-do a commit

git reset --soft HEAD~1

After pushing to your remote repo and this error appears:
! [rejected] master -> master (fetch first)

git fetch origin master # match the local repo commit status to the push destination     
git merge master #    
git push -u origin master  

# for non-fast-forward error  
git fetch origin master:tmp
git rebase tmp
git push origin HEAD:master
git branch -D tmp
git push -u origin master 

For fatal: refusing to merge unrelated histories error

git checkout master
git merge origin/master --allow-unrelated-histories
# or run this before your 'git pull origin master' command  
git pull --allow-unrelated-histories origin master 

If Github questions your user credentials.

git config --global user.email "<your email>" 
git config --global user.name "<your github user name>" 

When using SSH for your github remote repo, e.g. git@github.com:username/reponame.git

Generating a new SSH key

Accessing your SSH key:
- In Mac, in Terminal, type

cat ~/.ssh/id_rsa.pub  

• In Windows, in cmd, type

ls ~/.ssh/*.pub   

1. Go to the repo loading page on your Github

2. Drag and drop the file/s onto the screen

3. Add a commit message, e.g. 'init' 'updated table2', etc

Why am I telling you this?

I'd rather you move towards open-access and reproducible research than be deterred by the git user experience.